Thinking about this some more, I don't think it's necessary to find the geth commit as all we need is the latest renaming commit. I think the whole thing can be reduced to a single line:

git rev-list --author "github-actions\[bot\]" --grep renam -n 1 origin/main

Then both scripts can be deleted. I haven't checked the exact line above as I'm on my phone, but the general idea is sound IMO. Using "renam" catches both "rename" and "renaming" in case somebody changes it in the future, but probably best to add a comment on that workflow stating that it MUST include it.

That's great! Although I would keep the grep to the full \[AUTO\] rename Go module + update internal import paths and specify in the job where that string is defined to mirror it, to avoid it catching the wrong commit (github bot might be renaming something else)

That's great! Although I would keep the grep to the full \[AUTO\] rename Go module + update internal import paths and specify in the job where that string is defined to mirror it, to avoid it catching the wrong commit (github bot might be renaming something else)

Let's use "rename Go module" then as it's the shortest string that's specific to what we're looking for.